-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Github Action #224
Update Github Action #224
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As previously mentioned I don't think we should consider 8.13 the default branch but work on recreating some main branch that should be the default branch or update the default branch to 8.16 and add a task in our bumping process to switch default branch each time we publish a new minor release.
@jmlrt Thank you, and yes, I agree with your suggestion as I found this a bit confusing from my previous work on the repo. I am not fully aware of why we have no main branch in this repo like others. I will focus on this after Milestone Release as it is out of the scope of my previous ticket that led to this discovery. So do you see value in updating this branch? I wanted to update it so I can compare it to latest branch 8.16, and from there set 8.16 as default of create main depending on which one will work best. |
Let's merge this one, can you create a follow-up jira for setting a main branch or a process to always have the latest branch as default and we should be good 🙏🏻 |
This commit was created by the elastic-dockerfiles-publisher. Co-authored-by: Elastic Machine <[email protected]>
|
Given that this is considered as "default" branch of this repository, I am updating the GitHub action, to reflect recent changes #221